I think that a standard is arising on the way a method is injected with a request bus. My naming was requestContext and I believe mach-ii and fusebox use both event. I think it would be benefitial for developers for me to change this to event. What are your thoughts on this? This would help if a developer wants to switch from one framework to another or doing a transition, if some of the similar elements shared in an MVC framework can remain the same. I am for changing it to event, but I would like to know you opinions?
Blog
Recent Entries
Introducing bx-jwt: Enterprise-Grade JSON Web Tokens for BoxLang 🔐
JWT authentication is everywhere. But rolling it correctly — with proper algorithm enforcement, key management, clock skew handling, JWE encryption, and zero security footguns — is anything but trivial. Today, we're shipping bx-jwt, a production-ready JWT/JWE module for BoxLang that handles all of it out of the box, so you can focus on building, not fighting cryptography.
Luis Majano
Luis Majano
May
22,
2026
What “Modernize or Die” Really Means in 2026
“Modernize or Die” is not about forcing teams into MVC, chasing trends, or rewriting every CFML application from scratch. It means making sure your applications, teams, and processes can survive the future: easier to maintain, test, secure, deploy, document, hire for, and evolve. In 2026, modernization is less about adopting the newest pattern and more about reducing business risk, protecting the value already built into your systems, and ensuring CFML applications remain credible, sustai...
Cristobal Escobar
Cristobal Escobar
May
22,
2026
Free Webinar: Making AI useful for CFML/Java developers in Real Applications with BoxLang!
AI is everywhere right now, but for many development teams, the biggest question is no longer “What is AI?” it’s “How do we actually use it in real applications in a secure, practical, and maintainable way?”
Maria Jose Herrera
Maria Jose Herrera
May
20,
2026
Add Your Comment
(5)
Feb 27, 2007 14:48:06 UTC
by Sana
Hi Luis,
This makes perfect sense, should have some compatibility to other frameworks, at-least vocabulary should be same, so new developers adopt more easily.
Feb 27, 2007 16:20:13 UTC
by Sami Hoda
Can this be a customizable parameter instead?
Feb 27, 2007 18:07:03 UTC
by Luis Majano
I have been going over this and I think the best way is to just call the method and pass the argument. It would then be up to the developer to name the argument. However, the type of the argument will always be: coldbox.system.beans.requestContext
How does this sound?
Feb 27, 2007 19:09:58 UTC
by Sami Hoda
I suppose that works. Whenever there is a chance for flexibility, I'm for it.
Mar 05, 2007 19:19:15 UTC
by tony petruzzi
Actually most of the other frameworks let you change the name to whatever you want, they just use event as the default. But you are correct when saying that this would make it alot easier to transition from one framework to another.
BTW great work. ColdBox is getting more and more attention lately. I haven't heard anything coming out of the Model-Glue camp.